home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
United Public Domain Gold 2
/
United Public Domain Gold 2.iso
/
utilities
/
pu295.dms
/
pu295.adf
/
Logging
/
VhfLog
/
VHFLOG.DOC
< prev
next >
Wrap
Text File
|
1988-12-18
|
4KB
|
97 lines
VHFLOG.BAS
Original program by Clarke Greene K1JX
Amiga version by John Gager K7KB
[See bug report at end of this file.]
This ARC file contains the Microsoft BASIC (tm) source code for the ARRL VHF
Contest log editing program listed in the "Contests" chapter of The ARRL
Operating Manual, Third Edition. The program takes an ASCII log listing (as
created by you with your favorite word processor), and produces a log package
suitable for submission to the contest sponsor. Three separate files are
produced:
1. A LOG file - (identified by the filename extension ".LOG"). This file
holds the actual log. New multipliers are identified and counted, and
duplicate contacts identified.
2. A DUPE SHEET file - (identified by the filename extension ".DUP"). This
file holds a dupe sheet as required by the contest sponsors. This is a
complete listing of all the contacts made on a particular band, in
alphabetical order.
3. A SUMMARY file - (identified by the filename extension ".SUM"). This
file holds a summary sheet for the band edited. Total valid QSOs,
duplicate QSOs, and grid squares worked are listed, as well as a
complete breakdown of QSOs per grid square.
The file containing the log entries must be an ASCII file in the
following format:
TIME CALLSIGN RCV'D REPORT
At least one space must be between each field of each log entry, and each line
must be terminated by a carriage return. Only a changed digit in the time
field must be present; for example, if the contest begins at 1800Z and the
first contact is made at 1802Z and the second contact is made at 1805Z, then
only 5 need be entered in the time field. If the third contact is made at
1812Z, then 12 should be entered in the time field. If the next contact is
made at 1812Z, then no number need be entered in the time field (however, be
sure to enter a space to indicate separation between fields).
The three output files (.LOG, .DUP, and .SUM files) can be printed by using
the Amiga "TYPE" command.
Some reminders:
1. Be sure your log is in an ASCII format. Just about every word processor can
operate in an ASCII or Non-Document mode - that should work fine. As an
alternative, you can use one of the many utilities available in the
marketplace and in the public domain to convert your word processor output
into an ASCII format.
2. If you enter the callsigns in your log in lowercase, they are automatically
converted to uppercase for the final .LOG file.
3. Each band requires a separate entry file. The output files will be named as
the original filname plus the appropriate extension (for example
JUNE144.LOG, JUNE144.DUP, and JUNE144.SUM would be produced from the log
entry file JUNE144). As a consequence of this, any file with the same name
will be overwritten when VHFLOG is run. To avoid any deletion of valid
files, use unique names for the files used on each band, and don't use the
extensions .LOG, .DUP, or .SUM.
Special notes for the Amiga version
-----------------------------------
This ARC contains 3 files:
VHFLOG.BAS - AmigaBasic program
VHFLOG.DOC - This documentation file
VHFLOG.DAT - A small log file used to show example log entrys and to test the
VHFLOG.BAS program.
To give credit where credit is due, this program is by Clarke Greene K1JX.
The only thing I've done is go through his program and make it more agreeable
with AmigaBasic, and add a few minor features along the way. I really haven't
had a chance to test this program throughly since I don't get into contesting
very much, but I believe it is free of any major bugs. If you find any bugs
that I have missed, or have suggestions and comments about these programs,
please let me know.
73,
John Gager K7KB
Compuserve ID 71336,624
Amiga features include:
* Automatic capitalizing of entries read from log source file.
* Automatic capitalizing of keyboard entries from program prompts.
* Expanded error checking for improper data read both from the log
source file and the keyboard.